Feature 21955 - Manage the local administrators on Microsoft Entra joined devices #708
Feature 21955 - Manage the local administrators on Microsoft Entra joined devices #708
Conversation
|
@merill @ramical
The current test fails organizations that implemented this recommendation. |
ramical
left a comment
There was a problem hiding this comment.
Added a couple of comments. Once you address, pls check in
@ramical Any comment on this? |
|
Fair point and thanks for connecting the dogts. This is a great cross-pillar scenario where we can use some advice from our Intune specialist. @Clay-Microsoft wondering if you can weigh in? From Entra, we have policy plane to inject local admins to entra devices and seems that intune does too. So what's the best practice here? |
@Clay-Microsoft - Need you inputs on this. |
|
Response from Clay - "Account protection policies via Intune are generally the preferred and better path. That is what we recommend." |
There was a problem hiding this comment.
Pull request overview
This PR rewrites the assessment logic for Test-Assessment.21955 to check if local administrators on Microsoft Entra joined devices are properly managed by querying role assignments from the database instead of querying a device registration policy API endpoint.
Changes:
- Replaced Graph API policy check with database query for Microsoft Entra Joined Device Local Administrator role assignments
- Added detailed reporting tables showing active (permanent) and eligible role assignments with user/group details
- Updated documentation to provide more comprehensive security threat context
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/powershell/tests/Test-Assessment.21955.ps1 | Rewrote assessment logic to query vwRole database view for role assignments instead of device registration policy, added detailed reporting with tables for permanent and eligible members |
| src/powershell/tests/Test-Assessment.21955.md | Expanded threat description with detailed attack scenario explanation, updated documentation link |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
alexandair
left a comment
There was a problem hiding this comment.
@praneeth-0000
Please, address my feedback.
alexandair
left a comment
There was a problem hiding this comment.
@praneeth-0000 Please, address my feedback.
|
After discussing the @ramical and @KalwaniRavi we've decided to make one more change to this test. If the tenant has any Intune licenses, this test should be Skipped with the reason as 'Not applicable for tenants with Intune'. This is because the other intune test 'Local account usage on Windows is restricted to reduce unauthorized access' handles the scenario. |
bcd7af5 to
0831076
Compare
Rewrote the assessment logic as per new spec
Closes #678